🔴 Missing convert-oklch preprocessor on vscode platform causes broken color values in tokens.json

The vscode platform (lines 224-238) uses transforms.colorRgb which relies on tinycolor2 for color parsing, but does not have the convert-oklch preprocessor registered. The code's own comment at packages/tokens/src/build.ts:72-75 explicitly states: "Style Dictionary's built-in colorRgb transform uses tinycolor2, which does not support the oklch() color format." The convert-oklch preprocessor was created for exactly this reason and correctly added to the js platform (line 200), but was omitted from the vscode platform. Since the source includes tokens/color-primitives.default.json (which now contains oklch values), and the vscode file has no filter excluding color tokens, all oklch primitive tokens will pass through colorRgb unconverted. tinycolor2 will either leave them as raw oklch strings or produce incorrect RGB values (e.g., rgb(0, 0, 0)). The resulting dist/tokens.json is explicitly exported in package.json and consumed by external tools.

Was this helpful? React with 👍 or 👎 to provide feedback.

Missing oklch preprocessor on vscode platform

High Severity

The vscode platform uses transforms.colorRgb (which relies on tinycolor2) but doesn't include preprocessors: ['convert-oklch']. The js and figma platforms both correctly include this preprocessor for the same reason. Since tinycolor2 cannot parse oklch() values, color tokens in the tokens.json output will either be raw oklch strings or silently converted to black, producing incorrect colors for VS Code consumers.

 

^{Reviewed by Cursor Bugbot for commit ee2d0bf. Configure here.}